-
-
Notifications
You must be signed in to change notification settings - Fork 41
Improved Pandora Extensions Settings #230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
trobugno
wants to merge
19
commits into
bitbrain:godot-4.x
Choose a base branch
from
trobugno:pandora-extensions-settings
base: godot-4.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Improved Pandora Extensions Settings #230
trobugno
wants to merge
19
commits into
bitbrain:godot-4.x
from
trobugno:pandora-extensions-settings
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bitbrain
reviewed
Nov 17, 2025
Owner
|
Thank you for raising this. I will check this out locally and play around with it. |
Added field_settings. In this way you can customize the behaviour of any custom properties.
trobugno
added a commit
to trobugno/pandora_plus
that referenced
this pull request
Nov 30, 2025
### What's new? - Created **configuration.json** following the new **Custom Extensions Settings** introduced by me in Pandora addon. - Renamed all property types adding the suffix **_property** to aligned them with new settings. - Done a fixes to autoloads when the plugin is enabled. ### Notes - This build uses an unapproved version of the Pandora addon. To view the PR I created, follow the [link](bitbrain/pandora#230)
…value() of property.gd
Added missing close_requested when user click on 'Close' button
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pandora Extensions Settings - Improvement
Added more dialog to help user the creation of custom property, dependency, etc.
Pandora Bug Fixes
Issues Fixed
Issue n.1: Resource Properties Not Displaying in Editor
Symptom: When selecting a resource (e.g., texture) for a property in Pandora's editor, the field remained empty and the error
ERROR: Resource file not found: res://appeared in the console.Root Causes: Multiple interconnected issues in the resource property handling system:
parse_value()resource_pathmetadataIssue n.2: Subcategories and Entities Sharing Data (Reference Sharing Bug)
Symptom: When creating a subcategory (e.g.,
AlchemyRecipesas child ofItemRecipes) and configuring properties, all child entities and the category itself shared the same data. Modifying one entity would modify all others.Root Cause: In Pandora's inheritance system,
get_default_value()returns the same object reference from the parent if there's no override. UI components directly assigned this reference tocurrent_property, causing modifications to be applied to the shared object before an override was created.Solution: Added
duplicate()method to all custom property classes and modified UI components to work with copies instead of direct references.Files Modified
1.
model/types/resource.gdChanges:
parse_value()to prevent loadingres://nullhandling inwrite_value()is_valid()to accept both Resource objects and String pathswrite_value()for path valuesCode:
2.
model/entity.gd-OverridingProperty.get_default_value()Changes:
parse_value()for type conversionnil, now passes{})ObjecttoRefCountedto avoid duplicating ResourcesCode:
Note: The duplication fix is critical for preventing reference sharing in custom RefCounted classes while preserving Resource integrity.
3.
ui/components/properties/resource/resource_property.gdChanges:
refresh()call after value changerefresh()to access raw override values directlyCode:
Rationale: Accessing raw values prevents
parse_value()conversion which can cause Resources to lose theirresource_pathmetadata due to Godot's resource caching behavior.4.
ui/components/resource_picker/resource_picker.gdChanges:
set_resource_path()Code:
Technical Explanation
The Resource Path Problem
When a Resource is loaded via
load()and then retrieved viaget_default_value(), Godot's resource caching system may return a Resource instance with an emptyresource_path. This happens because:resource_pathproperty can be empty for cached instancesThe Solution: String as Source of Truth
Instead of storing the loaded Resource object, we store the path as a String and convert it to a Resource only when needed:
_property_overridesparse_value()converts String → Resource when game code accesses itwrite_value()ensures String format for serializationThis approach ensures the path is always available for display while still providing proper Resource objects to game code.
Impact
These fixes resolve:
res://loading errorsBackward Compatibility
The changes are backward compatible:
write_value()is_valid()change accepts both formats